Add support for UV dependency management #2601
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevinjqliu
reviewed
Oct 26, 2025
There was a problem hiding this comment.
Thanks for working on this!
I tested a few things locally.
- all the
makecommand - side by side pyproject.toml comparison
- ran a few github workflows on my forked repo
python-ci.yml✅python-ci-docs.yml✅nightly-pypi-build.yml❌ (something weird with cibuildwheel)
We might want to rebase this PR to capture of of the recent changes, such as the 3.9 deprecation. I'm not too worried about the library versioning since the dependabot workflow will upgrade them again
btw, there are a still references to poetry in mkdocs/docs/contributing.md
|
i cant seem to get |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2553
Rationale for this change
During the release process cleanup, I also had prototyped a migration from Poetry to UV. I used the https://github.com/mkniewallner/migrate-to-uv package to migrate to UV and ran a release workflow and some others like doc serve for validation.
This PR also migrates the Makefile to use UV. I'll still need to upgrade the docs to reflect the UV contribution workflow. I think it would be a good start to push up as a prototype, and have others checkout and give it a try.
Build System Changes
Build Backend
UV doesn't have a build backend like poetry that supports hooks or custom build scripts. So I've switched to use Hatchling as the build backend with the existing (
build-module.py) to ensure Avro files are properly compiled and included.Build Verification
Release builds can be verified using:
Both commands ensure parity with the previous Poetry build outputs.
Are these changes tested?
Yes
make installEnvironment setup and dependency installationmake test- Unit testsmake test-integration- Integration tests with all extrasmake lint- Linting and code quality checksmake doc-install && make doc-serve- DocumentationAre there any user-facing changes?
No user facing changes. Contributors will need to use UV instead of Poetry for development, but all make targets remain the same. So not really?